Enterprise service delivery technical architecture

ABSTRACT

An Enterprise Service Delivery Technical Architecture includes a Technical Model, and a Technical Delivery Framework, and is designed to facilitate the development of complete enterprise service management solutions. The use of the Enterprise Service Delivery Technical Architecture as the framework for an enterprise systems management technical solution results in solution designs created to be independent of the technology platform being managed with a view that meets the overall business requirements that span the technology platforms within a business environment. An information technology infrastructure already in place for a customer is analyzed and broken down to its very lowest level building blocks. Then the building blocks within the model of the technical architecture are mapped with the building blocks of the customer&#39;s information technology infrastructure to determine which of the building blocks of the model are to be used for the customer&#39;s information technology operation.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present invention is related to the following U.S. patentapplications which are hereby incorporated herein by reference:

Ser. No. 09/______ entitled “Method for Delivering a TechnicalFramework” (Attorney Docket No. AUS9-2001-0207-US1);

Ser. No. 09/______ entitled “Enterprise Service Delivery TechnicalFramework” (Attorney Docket No. AUS9-2001-0209-US1);

Ser. No. 09/______ entitled “Enterprise Service Delivery TechnicalModel” (Attorney Docket No. AUS9-200-0210-US1).

TECHNICAL FIELD

The present invention relates in general to the management ofinformation technology systems.

BACKGROUND INFORMATION

The traditional approach to managing computer systems has been to designand deploy the management system based primarily on which particulartype of hardware platform that the subject systems execute on. Forexample, systems management solutions may be focused on mainframecomputers, mid-range computers, networks, LANs, etc. This is a purelytechnology based approach to systems management which does not align themanagement of the system to the business functionality of the system orthe business requirements of the user of the system. The result of thisis that management staff become increasingly remote from the businessthat the information technology (“IT”) supports, which in turn resultsin a lack of awareness and understanding of the business challengesfacing the end users.

For example, some companies derive a significant percentage of theirrevenues from strategic outsourcing services provided to othercompanies, such as banks and other financial institutions, which arelargely dependent upon information technology to support their productsand services to their customers. After such a bank contracts with thestrategic outsourcing services of a service provider, it will then go inand hire most of the staff who had been previously running theinformation technology shop at the bank, and attempt to consolidateequipment and operations more efficiently. Quite often, such informationtechnology shops have grown up from being very small, relying uponindividuals more than process. Additionally, systems, hardware,software, and processes will not be that well documented, quite franklybecause the people who have developed the IT for the bank have beenthere for so long that they keep it all in their heads. The advantagethat the outsourcing company can bring to this situation is that it hasinvested considerable research and development into defining processesaround these type of IT disciplines, such as data storage and outputmanagement, system administration, event management, paging andescalation, security management, operations automation, change orders,etc. The outsourcing company will enter the situation and often applysuch process to more efficiently operate the information technologyalready existing within the bank's technology systems. Payment is inmany different ways, such as on a per workstation basis, per serverbasis, number of employees needed, etc. The whole operation will then berun for the bank, including problem and change management around thatstructure, often including 24-hour assistance and a help desk.

The problem with this process in general is that it has to be reinventedeach time the outsourcing company goes into a new outsourcingarrangement with a new customer. The reason is that different companieshave disparate tools. For example, one company may use Microsoftproducts, while another company uses Lotus products. One company may useHitachi mainframes, while another company may use IBM mainframes. Evenwithin one particular information technology system within a company,disparate systems, software, and hardware may be used among the variouslocations. There is some advantage that the outsourcing company canemploy by having the same employees cover the information technologyneeds of a multiple of companies by sharing their time among thosecompanies. However, the design of the outsourcing operation still isoften done on an ad hoc basis, dependent upon the particular systems inplace at the new customer.

Therefore, what is needed in the art, is a way for an outsourcingcompany to leverage from the knowledge gained while performing suchoutsourcing services from one client to the next.

SUMMARY OF THE INVENTION

The present invention addresses the foregoing need by providing anEnterprise Systems Delivery (“ESD”) Technical Architecture (“ESDTA”),which includes a Technical Model, and a Technical Delivery Framework.The ESDTA is designed to work within a high-level framework tofacilitate the development of complete Enterprise Systems ManagementSolutions. Thus, the use of the ESDTA as the framework for an EnterpriseSystems Management Technical Solution results in solution designscreated to be independent of the technology platform with a view thatmeets the overall business requirements that span the technologyplatforms within a business environment.

More specifically, an information technology infrastructure already inplace for a customer is analyzed and broken down to its very lowestlevel building blocks. Then the building blocks within the model of thetechnical architecture of the present invention are mapped with thebuilding blocks of the customer's information technology infrastructureto determine which of the building blocks of the model are to be usedfor the customer's information technology operation.

An advantage of the present invention is that a technical model of anEnterprise Systems Management Architecture is consistently reused foreach new information technology outsourcing customer in a consistentmanner, which enables the company providing the outsourcing services toleverage the model and the resources needed to implement the variousdesign objects used within the model.

Adoption of the present invention establishes a framework for the futurehelping an information technology outsource services provider take onthe right business profitably and guide implementation of IT solutions,a common technical vision for the outsourcer and its customers, arational use of technology, within which IT requirements can beimplemented with the confidence that the architectural components willwork together, and a range of options, giving the outsourcer the abilityto react quickly to changes in business requirements. For designers oftechnical architectures, there is a standard framework with reusablecomponents within which to construct a solution. For delivery staff,there is a repeatable solution with standard methods and procedures. Forthe outsourcer, there is a strategic solution to meet the requirementsof the customer and a solution with an optimal cost profile. Forcustomers, there is the benefit of exploiting state-of-the-arttechnologies in a consistent way that brings added value to their ITservices.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the invention that follows may be better understood.Additional features and advantages of the invention will be describedhereinafter which form the subject of the claims of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an exemplary customer information technologyinfrastructure;

FIG. 2 illustrates a flow diagram configured in accordance with anembodiment of the present invention;

FIG. 3 illustrates an ESD Technical Architecture configured inaccordance with an embodiment of the present invention;

FIG. 4 illustrates an ESD Technical Architecture logical levelconceptual model;

FIG. 5 illustrates an exemplary architectural building blockdecomposition;

FIG. 6 illustrates an exemplary level 1 ABB relationship table;

FIG. 7 illustrates an exemplary level 1 ABB relationships schematicrepresentation;

FIG. 8 illustrates a method in accordance with an embodiment of thepresent invention;

FIG. 9 illustrates an exemplary inventory of hardware of a customer;

FIG. 10 illustrates lowest level ABBs;

FIG. 11 illustrates mapping of lowest level ABBs to inventory;

FIG. 12 illustrates design object relationships;

FIG. 13 illustrates ABBs identified to deliver services;

FIG. 14 illustrates an example of ABB lists and relationships;

FIG. 15 illustrates logical groupings of ABBs;

FIG. 16 illustrates tool selection based on design objects;

FIG. 17 illustrates an exemplary detailed technical design with designobjects; and

FIG. 18 illustrates a data processing system configured in accordancewith the present invention.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forthsuch as specific IT configurations, etc. to provide a thoroughunderstanding of the present invention. However, it will be obvious tothose skilled in the art that the present invention may be practicedwithout such specific details. In other instances, well-known constructshave been shown in block diagram form in order not to obscure thepresent invention in unnecessary detail.

With the advent of e-business, which in most cases has to compete withtraditional “non-e-businesses,” the fundamental, underlying operationsof many companies have changed. Although many of these companies verysuccessfully had their act together when they, were not e-businesses,they may not have mastered the exploitation of the underlying technologyto the point they were at prior to adopting that technology. Because ofthe increasing complexity of the underlying technology and the total“interconnectedness” of that technology with core business processes,many of these companies have been faced with a particularly difficultproblem—that of building and maintaining a workforce that includespeople who can translate business into technology in order to keep theirunderlying business processes executing effectively within an e-businessframework.

As these companies must also compete with “non-e-businesses,” they havenot only had to struggle to keep their underlying business operationseffective, they have also had to focus on what “non-e-businesses” focuson, which is the customer experience. The successful companies haveleveraged the skills of outsourcing and outtasking partners to maintainthis dual focus on both maintaining the effectiveness of their businessoperations, as well as focusing on the new, electronic storefront. Thesuccessful e-businesses are rapidly turning “non-e-businesses” into“non-businesses.”

Notice that in the last two or three paragraphs the word effective wasused a few times, but the word efficient does not appear. This was bydesign, as there are many successful e-businesses that are effective,but that are not efficient. There is a fundamental reason for this. Thetraditional segmentation of “frontroom” and “backroom” functions is nolonger possible when faced with new technology. More accurately, the“effectiveness bar” has been raised. Walls are falling. Sales can nolonger be totally disjoint from finance, procurement can no longermerely throw product over the wall to sales. Companies must now take amore “holistic” or “end-to-end” view of their business. This overall,end-to-end view is how their customers see their business. Hence thefocus on end-to-end management from a customer-centric view.

Perhaps holistic is not quite the correct word. The real definition ofend-to-end or enterprise systems management is more circular thanholistic. End-to-end management, enterprise systems management, merelymeans the management of what is important to the enterprise, between twowell-defined end-points.

This does sound confusing, but it should not be. For a small business,the entire, end-to-end enterprise may be only a cash register and abackroom PC used to keep track of accounts payable and receivable. For alarge multinational company, end-to-end may encompass all the supportingsystems that make the purchase of a product through the Internetpossible, including the front-end Web presence, the ordering andprocurement system, the inventory system, the financial system, andpotentially, connections or touch-points to systems outside of thatcompany's control, such as EDI links, or real-time transactionconnections to other companies. Beyond even those boundaries, anend-to-end enterprise could arguably include all business-to-business(B2B) and customer-to-business (C2B) systems and links.

As would be expected with something that could be as small as onemachine or as large as the Internet, and potentially as complex asmanaging both the systems providing the customer experience and thebusiness operations systems, there is not a “one-size-fits-all” solutionfor managing these disparate enterprises. Each overall, end-to-endenterprise systems management solution is, in fact, a unique solution.

This has challenged businesses, and particularly outsourcing andouttasking service providers, for quite some time. Businesses are builton the foundation of leveraging commonality of resources and knowledgeto excel in service to customers. If each end-to-end systems managementsolution is unique, it is difficult for a service provider to continueto provide customers with the benefits of economies of scale andleveraged skills.

There are three terms in the following paragraphs: Framework, band ofstandardization, and standard methods. A framework is a fundamental andbasic arrangement of subcomponents or parts. A framework typicallyidentifies how those parts fit together at the highest level. Any largeIT organization realizes that all systems management solutions that itdeploys cannot be identical. Standards developed must allowcustomization, while maintaining the optimum identified level ofstandardization. That optimum level is known as the band ofstandardization. Another key is the development of standard methods.Even though a company may have a consistent, standard framework andclear definitions of the band of standardization, each group thatdeploys solutions within the framework must do so in a repeatable andconsistent manner to maintain an advantage. That consistency is providedthrough standard methods for definition, deployment, and operation ofthe solution. For very large organizations, the major opportunity liesin a fourth term: leveraged knowledge. No individual department ordelivery segment or organization can match the knowledge contained inall departments and delivery organizations combined. The difficulty, ortrick, is to leverage that knowledge across the entire organization.

A framework adopted by the present invention for end-to-end EnterpriseSystems Management is the Enterprise Systems Management Architecture(ESMA) Solution Framework. Here are a few definitions that will help inunderstanding the framework. The term enterprise in traditional use mayidentify any individual undertaking. The term enterprise may alsoidentify a complete business. Within the context of the ESMA SolutionFramework (and ESMA in general) an enterprise is comprised of thosebusiness undertakings defined as important to customers. Customersdefine what an enterprise is to them. This may be as small as a singleserver, or as large as an integrated manufacturing and distributionapplication. A system, within the context of ESMA, is a combination ofsoftware and hardware focused on providing a specific function.Management is the practice of administering, operating, and controlling.End-to-end within the context of systems management, has at least twosimilar and complementary meanings. From a transactional perspective,end-to-end means “from the beginning of the transaction through tocompletion of the transaction.” From a systems perspective, end-to-endmeans “all-inclusive and all-encompassing.” From an ESMA perspective,end-to-end means both of these things. End-to-end is viewing an entireenterprise system as a total entity, not separated by artificialdelineations such as software or hardware platform. When an enterprisesystem is viewed based on the transactions that that system supports,end-to-end implies viewing that transaction from initiation throughcompletion. To really adopt an end-to-end view, some context of eitherthe enterprise (“what is important?”, “what is the undertaking?”) or theactual transaction (“how does it start?”, “where does it end?”) isapplied.

From a general industry perspective, Enterprise Systems Management (ESM)is the ability to support key business processes by efficiently managingthe underlying IT infrastructure from end to end, regardless of platformESM requires a complete set of processes, tools, and information thatenables people to effectively manage all of their information technologyresources, thereby providing the ability to support key businessprocesses.

The term architecture is very much overused in the informationtechnology industry. In terms of ESMA, adding the term architecture toEnterprise Systems Management implies that all those things which arefocused on Enterprise Systems Management are architected, or aredesigned in an integrated, coordinated manner, with some overall “bigpicture” in mind.

In the context of ESMA, a solution is a combination of ESMA components(processes, tools, people, and information) focused on solvingcustomers' systems management problems. For example, a solution may befocused on solving the problem of managing changes to a customer's ITenvironment. A framework is a fundamental and basic arrangement ofsubcomponents or parts. A framework typically identifies how those partsfit together at the highest level.

The ESMA Solution Framework is the fundamental and basic arrangement ofall of the subcomponents or parts of each Enterprise Systems ManagementSolution.

The ESMA Solution Framework

There are many ways in which one could define the framework fordelivering end-to-end Enterprise Systems Management Solutions. Althoughthe ESMA Solution Framework is only one of those, the present inventionadopts the same focus as e-business customers, focusing on both thecustomer experience (or the “relationship”) and the “backroomoperations” (the “infrastructure”).

Relationship Management

In the context of ESMA, Relationship Management is the practice ofadministering, controlling, and operating the relationship betweenorganizations using solutions defined within the ESMA Solution Frameworkand the customers of those organizations. Relationship Management istypically outwardly focused, or focused not on the actual management ofsystems, but focused more on the stated concerns of the customer andcontrolling external factors related to Systems Management, such ascontrolling change. A major element, or goal, of Relationship Managementis maintaining and enhancing the effectiveness of overall SystemsManagement.

Infrastructure Management

In the context of ESMA, Infrastructure Management is the practice ofadministering, controlling, and operating the underlying customerinfrastructure making up their enterprise. Infrastructure Management isprimarily inwardly focused, or focused specifically on managing theunderlying systems. Rather than focus on stated concerns of customers,in conjunction with Relationship Management, those stated concerns aretranslated into infrastructure-focused actions, or actions intended toensure the ongoing “health” of the infrastructure. A major element, orgoal, of Infrastructure Management is maintaining and enhancing theefficiency of overall Systems Management.

Service Management

In the context of ESMA, Service Management includes all activitiesassociated with the administration, control, and operation of allcustomer-contracted services. This may include joint definition ofstrategies and standards with the customer. This definitely does includeimplementing Systems Management solutions focused on applying thedisciplines of Systems Management. In short, Service Management issatisfying, or delighting, customers, including Relationship Managementand Infrastructure Management.

Disciplines

A discipline is the logical grouping of ESMA components (Process, Tools,People, and Information) that address distinct planning, control, andoperational objectives. When solutions defined as part of a particulardiscipline are implemented, they satisfy a functional objective ofEnterprise Systems Management.

Disciplines defined within the ESMA Solution Framework include.

-   -   Data, Storage, and Output Management    -   Administration    -   Event Management, Alerting, Paging, and Escalation    -   Security Management    -   Operations Management and Automation    -   Capacity and Performance Management    -   Business Process and Application Management    -   Request Management    -   Decision Support    -   Knowledge Management    -   Asset Management    -   Call Management    -   Problem Management    -   Change Management

Data, Storage, and Output Management

This discipline is focused on the management of all data, includingeverything from complex relational databases on the high end of thescale down to tapes and disks on the low end of the scale. Thisdiscipline also includes the management of the underlying storagesystems, back-up of data, and output of data through approaches such asthe management of print operations.

Administration

This discipline is focused on the underlying administration of thedelivery of Enterprise Systems Management solutions provided to ourcustomers. Administrative functions such as planning, managingprocesses, deployment testing, controlling continuity (or disasterrecovery), handling skill requirements, and controlling service levelsare covered by this discipline.

Event Management, Alerting, Paging, and Escalation

An event is an indication of a change of state within a monitored systemthat may or may not be relevant to the overall management of acustomer's Enterprise System. This discipline is focused on the captureof events, determination of relevance of events (filtering andcorrelation), initiation of action (either through automation or throughalerting or paging), automated monitoring and reporting of progresstoward final disposition of events (escalation), and final dispositionof the events.

Security Management

This discipline is focused on all aspects of Systems ManagementSecurity, from user ID administration through overall physical andlogical security. This discipline includes planning for security andmonitoring security, as well as such specific techniques as intrusiondetection and ethical hacking.

Operations Management and Automation

This discipline is focused on exploiting automation to build, maintain,manage, and run customer operating environments. This disciplineincludes automated job scheduling and monitoring, both within a singleoperating environment and across operating environments. It alsoincludes distribution and implementation of the operating environment.Because an end-user's desktop is that end-user's operating environment,this discipline includes the use of such tools and techniques as desktopsoftware distribution and desktop remote takeover.

Capacity and Performance Management

This discipline is focused on measuring, reporting, and managing theoverall performance of a system. This performance may be at thecomponent level, across a subset of all components, or across all thecomponents that make up the customer's enterprise. The primarydifference between Capacity Management and Performance Management isthat Capacity Management is primarily focused on acquiring or retiringcomponents (building the environment), while Performance Management isfocused on monitoring, managing, and tuning the components that are inplace.

Business Process and Application Management

This discipline is focused on managing the systems supporting thecustomer's defined enterprise from a business perspective, based on theoverall business process being enabled by those systems.

Another term used to describe this concept is Business SystemsManagement.

This is significantly different than managing systems based on thetraditional, technology-biased views (based on technology or softwareplatform). Application Management is a subset of this discipline wheresystems are managed based on the application (rather than BusinessProcess) that they support. A Business Process is typically made up ofmany applications. This discipline includes what is traditionally knownas Availability Management, from the availability of components to theavailability of entire applications, through the availability of entireBusiness Processes.

Within the ESMA context, Business Process and Application Managementdoes not include the actual performance of the Business Process (forexample, running a procurement business for a customer) nor ApplicationManagement in the sense of application development and support. Thisdiscipline is focused on the Systems Management of the underlyingenterprise components as defined by a customer.

Request Management

This discipline is focused on receiving and managing customer requestsfor service. This may be as small as accepting the actual request andtracking fulfillment of that request. This may be as large as actuallyexecuting steps to fulfill the request that fall either inside oroutside of the other discipline areas.

Decision Support

This discipline is focused on using available, electronically storedinformation to enable end users to make better, more informed decisions.This discipline includes techniques and algorithms as simple as decisiontrees and drop-down lists. This discipline also includes complextechniques, such as data mining and the application of artificialintelligence.

Knowledge Management

This discipline is focused on the logical use of stored knowledge. Datais typically gathered from multiple sources and stored as data. Bycorrelating that data with other data and applying some context (such assource and location), that data becomes information. Knowledge isinformation that has been “filtered” by experience, or when deliveredelectronically, information that is entirely pertinent to the situationat the moment when the knowledge is delivered. Put another way,knowledge is acquired almost passively (you “know” something), whereasinformation is acquired actively (you are “looking” for information).Through complex artificial intelligence algorithms, electronicallydelivered knowledge will greatly reduce the requirement to actively“look” for information, providing knowledge at the moment that it isrequired.

Asset Management

This discipline is focused on the tracking of the full life cycle of apiece of hardware or software from the time of capital planning, throughprocurement, and final disposition or disposal of that asset. Thisdiscipline includes subcomponents such as asset inventory (includingwall-to-wall inventory methods), asset tracking, financial assetmanagement (including financial to physical reconciliation), andsoftware license management. This discipline also includes tracking andreporting of the logical and physical configuration of assets (what“makes up” an asset).

Call Management

This discipline is focused on the receipt and handling of calls fromcustomers. A call from a customer may be related to any other disciplineand may take the form of an actual telephone call, an e-mail, a fax, andso forth.

Problem Management

This discipline is focused on tracking, analyzing, and correctingincidents or problems. This discipline includes the short-termcorrection (through workaround) of problems, coordination of multiplecorrective actions, and broader scope approaches, such as “criticalsituation management.” This discipline also includes short-term analysis(such as problem determination) and long-term analysis (such as rootcause analysis) of problems.

Change Management

This discipline is focused on scheduling and tracking changes. Thisdiscipline includes such small changes as desktop changes (known asInstall/Move/Add/Change, or IMAC) and changes as broad as majorenterprise-wide changes.

Management Towers are logical groupings of the subcomponents of acustomer's enterprise, which roughly equate to the way that manydelivery organizations are organized to support information technology.This is primarily based on the physical architecture of the underlyingtechnical platforms. Management Towers are often also called Islands ofManagement because management within each tower is typically done in astand-alone manner, disjointed from the other islands. Management acrossthese towers in a consistent, efficient, and effective way is thefundamental goal of ESMA. The ESDTA has been designed to satisfy thatfundamental goal.

Referring to FIG. 3, the ESDTA 300 contains two major components, theESD Technical Model 301 and the ESD Technical Delivery Framework 302.The ESDTA 300 describes the structure of the complete set of technicalcomponents (models, frameworks, definitions, architectural buildingblocks, etc.) that an information technology outsourcer requires todeliver services. The ESDTA Vision 303 is to enable the rigorous andconsistent management of information technology services provided in aseamless manner across all platforms, leveraging resources anddelivering business value while driving toward computing as a utility.The ESDTA Scope 305 is the architectural foundation supporting servicedesign. The ESDTA 300 does not represent any part of the engagement orcontract process but provides guidance for the conversion of thecustomer's tool set into the agreed standard. ESDTA Objectives 304 areto provide an open framework for IT Resource Management that promotescustomer business objectives, minimizes the impact of implementation andtransition on both the customer and the service delivery provider,facilitates standard service delivery globally and facilitatesleveraging resources across traditional boundaries (technical,organizational, process, and informational). A strategy with the ESDTAObjectives 304 is to use consistent interfaces to facilitate a plug-infunctionality, and to adhere to appropriate industry standards.

Key Requirements 306 are that the ESDTA must enable delivery of servicefor multiple customer environments from a central point-of-control, fora single customer environment for multiple points-of-control in usingpoint-of-control combinations. But within the architecture, eachpoint-of-control solution may be viewed as the single means ofsupporting a given customer. Actual delivery of service may requirecombinations of points-of-control due to contractual, geographical,linguistic, and/or chronological requirements. Portions of the solutionfor a customer may be managed out of one delivery center while otherportions of the solution may be managed from other delivery centersrequiring fragmentation of the point of control to achieve the businessobjectives of the customer.

Principles 307 are underlying, general rules that are durable and havewide applicability across the architecture, such as that thearchitecture will enable a standard end-to-end scalable, integratedsolution applicable to all customers. Principles 307 must map to theRequirements 306, stand the test of time, and be seen to be true for allsolutions; as such they must stand up to any challenge. As thearchitecture evolves, Principles 307 must always hold true and cannot becompromised. All elements of the architecture inherent Principles 307. Afirst principle is motivation, which includes reducing the architecturecomplexity and infrastructure costs while supporting continuousimprovement by remaining flexible enough to use new technologies,reducing training and staffing costs, reducing system integration costs,and allowing the outsourcing entity to provide service to any customerset, regardless of size, geography or language, the nature of thebusiness, or technology or scope of the management services required.Another principle is integration which implies that the organization mayneed to be changed to cater for integrated delivery. Transition ofcurrent solutions may require additional investment to converge on thearchitecture, and there is a need for buy-in and commitment bymanagement of the customer.

Use of the ESD Technical Model 301 as the base for defining anddocumenting all capabilities required to deliver ESM services solves theproblem of not designing those solutions from an overall businessprocess perspective, encompassing management of all components requiredto support those business processes regardless of technology platform.The ESD Technical Model 301 was developed through extending the conceptscontained within the IBM consulting information technology architecturemethod to satisfy the unique requirements of ESM. From reviewing IBMintellectual capital related to the information technology architecturemethod, the application and extensions of the present invention areinnovative and original, utilizing the “breakdown” structure describedby that method in a way not done before to describe the capabilities orfunctions required to deliver ESM solutions. Within the ESD TechnicalModel 301, each of the critical technical capabilities required tocreate ESM solutions is defined as an Architectural Building Block(“ABB”) 308. ABBs are components of the architecture that aresufficiently modular and bounded to be described as self-containedentities. ABBs are used to construct logical views of the TechnicalArchitecture. Each ABB is independent of the underlying physicalimplementation and does not imply, or exclude, a specific physicalarchitecture. Each ABB is defined to encapsulate a function and todocument its relationships to other ABBs. Criteria for tool selectionare derived from the ABB and its relationships. Each high-level ABB 308has been decomposed into lower level ABBs which individually identifyall capabilities or functions required to provide ESM solutions. TheseABBs 308 have been decomposed to the lowest level of uniqueness offunction. The following are exemplary ABBs. The User InteractiveServices ABB describes technology that renders information into theformat needed for views. Views encompass the rendering of information ina way that the recipient of the information can use, based on therequirements of his or her role. The Access Services ABB describes thetechnology that provides common, standard, and open means for providingpaths to data and IT resources in a secure, controlled way. It includesdirectory and navigation services to enable other functions to accessdata consistently. The Integration ABB describes the requirements placedon technology to support the integration, via data translation,necessary for the use of information within and across managementcapabilities. The Data ABB describes the data characteristics and thetechnology used to manage that data. This is both management- andcustomer-related data. The Management Enablement ABB describes therequirements placed on technology to enable the management functionsdefined with the process architecture. By meeting these requirements,global IT resources can be supported by common, standard, and open meansand managed from a business process perspective. The global IT resourcesABB describes the entire collection of endpoint devices, computingplatforms, data, and infrastructure components identified by thecustomer for global services to manage, as well as all endpoint devices,computing platforms, data, and infrastructure components used to supporta business entity's IT services.

There are four levels of ABBs 308 within the Technical Model 301. Thehighest level of abstraction is the conceptual level or level 0. All themajor components described within level 0, and the relationships betweenthem, are depicted in the logical level 0 conceptual model illustratedin FIG. 4. FIG. 4 depicts the Technical Architecture 300 that supportsthe IT services provided. The architecture was designed to provideenterprise-wide, end-to-end services, not only from the technologyperspective, but with the business perspective in mind. A major benefitof the architecture is that it positions IT services to transitioncomputing functions from today's “technocentric” paradigm to a “utility”paradigm. It also offers an effective way to adopt the tenets of“zero-latency” for IT services. The global adoption of the architecturewill support the seamless delivery of services across multiplegeographies. The present invention uses an organized and consistent setof policies, standards, protocols, and published interfaces to selecttechnical components that support the Enterprise Systems Managementprocesses. These technologies enable systems management by means of thefollowing capabilities. The user interface is the technology thatrenders information to and from the user into the format needed forviews and for the applications. Views encompass the rendering ofinformation in the way that the recipient can use, based on therequirements of his or her role. Access is the technology that providescommon, standard, and open means for providing paths to data and ITresources in a secure, controlled way. Integration is the requirementsplaced on the Technical Architecture 300 to support data and applicationintegration necessary for the interaction across functional entities.Data is the technology that supports the actions performed against theEnterprise Data Repository (EDR). The EDR contains the informationrequired for the delivery of ESMA services. The logical structure andcontents of the EDR are described by the ESMA Information Architecture.Management enablement are the requirements placed on technology toenable the application components defined within the processarchitecture so that global IT resources can be supported in a common,standard, and open means and managed from a business processperspective. Global IT resources are the objects being managed.

To illustrate decomposition of the ABBs 308 depicted in the logicallevel 0 conceptual model diagram of FIG. 4, FIG. 5 illustrates a sampledecomposition tree for one of the level 0 ABBs. Each ABB 308 is fullydocumented including a description, with what the ABB includes, what itexcludes, etc. One key element of documentation is the relationship thateach of the ABBs has to the other ABBs. This information is critical todesigning complete ESM solutions utilizing the ESD technical deliverframework design method. These relationships have not only been capturedwithin the conceptual diagram in FIG. 4 and within the documentation ofABBs, but also utilizing the following exemplary table illustrated inFIG. 6. And for level 1 ABBs, in the schematic diagram illustrated inFIG. 7.

The entire ESD Technical Model 301 has been developed to align with theESD Technical Architecture Vision 303, Scope 305, Objectives 304, andPrinciples 307, and to satisfy the ESD technical architecture identifiedKey Requirements 306.

Utilizing the ESD Technical Delivery Framework design methodology of thepresent invention, the Technical Delivery Framework 302 is created toreflect the individual requirements of each customer, while maintaininga direct relationship to the ESD Technical Model 301. The entityproviding outsourcing services, e.g., IBM, will maintain a template ESDTechnical Delivery Framework 302 which can then be modified to reflectindividual account or delivery center requirements. Each of theseTechnical Delivery Frameworks 302 will maintain the identifiedrelationships with the Technical Model 301. By maintaining therelationships to the Technical Model 301, the overall integrationbetween customers will be insured. The key to insuring that this mappingis maintained is the correct and complete identification of DesignObjects 313. Design Objects 313 are the basic foundation for all toolselection and design within each Technical Framework 302. Design Objects313 will be defined based on the Specific Solution Scope 317 for eachtechnical delivery and may be unique for each Technical DeliveryFramework 302. An individual Design Object 313 is a collection of“qualified” lowest level ABBs 308 with “attributes” added based on thespecific solution being developed. For example, if an ABB 308 entitled“Check Status” were selected for inclusion in a Design Object 313, itwould be “qualified” with a scope of what status is being checked (e.g.,are all servers “up,” did a job complete, etc.).

ABBs 308 are selected for inclusion in a Design Object 313 based oncommonality of either platform (where the actual ABB's associatedsystems management capability would execute) or function (a changemanagement design object). Design Objects 313 might be defined thatmapped one function to one tool (e.g., a Design Object 313 describingthe complete set of capabilities regarding problem management would mapto one, complete problem management tool). With current technology,there is a requirement to satisfy all the functional requirementsidentified within a Design Object 313 with integration or linkageprocesses.

The Relationships 312 between Design Objects, as well as the DesignObjects 313, lead to a revision of a set of template Tool SelectionCriteria 315 which have been developed to reflect the customers actualrequirements. By applying the Tool Selection Criteria 315 to SpecificSolution Requirements 314, within the Specific Solution Scope 317, toolsare selected that are totally integrated or integratable within eachTechnical Framework 302, and “top to bottom” within the ESD TechnicalArchitecture 300. A methodology in accordance with the present inventionis illustrated in FIG. 8. Each activity within this flow diagram isillustrated using a “swim lane” based process mapping technique referredto as the line of visibility engineering method (LOVEM). An object ofthe design methodology process in accordance with this embodiment of thepresent invention is defined in means by which technical servicerequirements can be mapped against components of the Enterprise ServiceDelivery Technical Model 301 to design a solution that is effective,efficient, and integrated with other ESM solutions previously providedby the outsourcing service provider (Blocks 801 and 802). The activitiesrequired to deliver specific services are used to select and “qualify”each ABB 308 required to deliver that service (Block 803). ABBs 308 arequalified by adding “attributes” that indicate how and/or against whatcomponent that the capability is being applied (Block 804). These ABBs308 are then grouped, based on commonality (of platform or function) toidentify Design Objects 313 (Block 805). Defining design objects 313 inthis way is a unique approach to designing ESM solutions. Tools(software) are then selected (Block 806) to satisfy the requirements inrelationships identified within and between these design objects 313.Gaps (Block 809) between requirements for tools and actual tools areidentified (Blocks 807, 808) to be filled with either skills, processesor integration. This approach is loosely based on the IBM ConsultingSystems Management Framework Design (SMFD) methodology, with significantextensions focused on utilizing the specific Technical Model 301 inaccordance with the present invention. The methodology of the presentinvention takes the design of the Technical Delivery Framework 302 to amuch lower level and never attempted using SMFD, and is fundamentally adifferent application of some SMFD concepts. Within the SMFD methodologythere is no concept of ABBs 308 or Design Objects 313. Once tools havebeen selected, and augmented by process changes, skills acquisition orintegration, satisfying all the relationships and requirements capturedwithin the definitions of the Design Objects 313, standard low-leveldesign techniques are utilized to determine placement and configurationof these tools within the target environment. The target environment isanalyzed and documented. The geographic location, size and capacity,etc. of each physical technical resource which is to be managed with theESM solution creates additional requirements on the actual physicaldesign of the ESM solution. The end result of utilizing the methodologyof the present invention within the overall ESD Technical Architecture300 is the creation of ESM solutions which are consistent in theirdelivery of services across all target environments, regardless ofplatform, using documented processes integrated with the selected toolset, both within individual customers, and across customers.

For a better understanding of the present invention, the followingexample is instructive. The Enterprise Service Delivery (ESD) TechnicalArchitecture 300 describes the overall structure including how the ESDTechnical Model 301 and the ESD Technical Framework 302 relate to eachother. The ESD Technical Model 301 is fairly static, and describes allof the components (people, process, tools and information) that are usedto deliver specific services to customers, as well as describing (ingeneric terms) the components of all customer environments.

A ESD Technical Framework 302 describes the actual systems managementsolution, or framework, that is used to deliver a set of specificservices to a customer.

The ESD Technical Delivery Framework Design Methodology describes how touse the relationships defined in the ESD Technical Architecture 300, andspecifically the ESD Technical Model 301, to develop a specific DeliveryFramework 320 (based on the ESD Technical Framework 302) for delivery ofa specific set of services for a customer.

Referring to FIG. 1, in order to describe, in “real world” terms,embodiments of the invention, examine an exemplary customer technicalenvironment. “Big World Bank” (BWB) is a company that has offices inEurope and North America. The main data center 101 for BWB is located inNew York. The New York data center 101 contains a large mainframeserver, and several smaller servers. There are many branch offices103-106 throughout the U.S. The European headquarters 102 for BWB is inLondon. At this site, there are several servers which provide computingpower to many offices 107-109 spread through the U.K.

Also referring to FIG. 2, BWB has decided that they wish to no longercompletely support their Information Technology (IT) environment withtheir own people, and have turned to an outsource service provider(e.g., IBM) to request that IBM (step 201) begin to provide two specificservices for their environment: Problem Management (identifying andsolving problems with the environment, discovering root cause,recommending changes, etc.) and Event Management (tied to ProblemManagement, but focused on immediate response, both automated andmanual, to electronic events that are detected in the environment—e.g. aserver goes down, creating an electronic event indicating that it can nolonger be “seen” on the network.) In order to provide these services,IBM must build a Delivery Framework 320 describing what people,processes and tools (and identifying information requirements) that willbe deployed to provide the desired functionality.

The ESD Technical Delivery Framework Design Methodology (TDF-DM) isfocused on identifying the specific tools, or technology, which will bedeployed to provide services for customers. When BWB approached IBM, IBMbegan to build documents and deliverables identified in the ESDTechnical Delivery Framework (TDF) based on the approach described bythe TDF-DM. The TDF is one of four (4) frameworks that were required toprovide service to BWB.

The next step (step 202) was to identify the specific Solution Scope 317as described in the contract, and based on common practices fordelivering certain types of services. For Problem Management and EventManagement, this would entail identifying hours of service, and whichcomponents (in general terms, such as “all NT servers”) which are inscope, etc. The next step (step 203) was to identify the SpecificSolution Requirements 314 for this solution. IBM went out to thecustomer site and inventoried every piece of equipment that was in thescope of the contract, including servers, workstations, network routers,hubs, etc. FIG. 9 illustrates an example of such inventory for BWB “inscope” hardware.

At this point, each component was mapped (step 204) to the lowest levelArchitectural Building Block (ABB) 308 described in the ESD TechnicalModel (ESDTM) 301. FIG. 10 illustrates an example of the lowest levelABBs 308 available in the ESD Technical Model 301. FIG. 11 illustratesan example of the mapping of each component in the BWB inventory (FIG.9) to the ABBs (FIG. 10). For example, there perhaps was a buildingblock identified as “Workstation”. Each workstation would be identifiedas being an instance of that ABB 308. In addition to being an instanceof ABBs 308, each inventoried component would also have certainattributes which would also be captured. Again using the workstationexample, in the ABB definition for a “Workstation”, it would beindicated that each workstation has attributes such as an OperatingSystem, a CPU, a Disk Drive, a Network Card, etc. Each of theseattributes would be captured.

As well as categorizing each component in the customer environment andassigning/identifying attributes, the relationships (Design ObjectRelationships 312) between these components would be identified (step205). For example, a workstation is connected to a hub, which is onetype of relationship. Another relationship would be what application aworkstation is implemented to support for a customer. FIG. 12illustrates an example of such identified Design Object Relationship 312for the BWB contract.

Once the entire customer environment in terms of ABBs have beendescribed, then the systems management ABBs in the ESDTM are looked atthat were required to provide the specific Problem and Event Managementservices. For example, it was known that a component described by an ABBwould be needed that would provide the capability to store and forwardevents. FIG. 13 illustrates an identification of which ABBs 308 from theTechnical Model 301 were needed to deliver the “in scope” services ofBWB. FIG. 14 illustrates examples of ABB Lists and Relationshipsindicated in FIG. 13.

When all of the ABBs were identified that were needed to provide Problemand Event services, then all of the ABBs were mapped describing the BWBenvironment, and all the systems management ABBs in the model together,based on the relationships of the customer ABBs and the relationshipscontained in the model. At this point, there was a consistent model forthe entire systems management solution for Problem and Event Managementfor BWB, that was also consistent with the overall model (ESDTM) fordelivering service. This complete model was made up of Design Objects313 based on logical groupings of ABBs 308. FIG. 15 illustratesidentified Design Objects 3/3 for the “in scope” services based onlogical groupings of ABBs 308 for the BWB example.

The consistency of the Technical Model 301 was ensured throughmaintaining the groupings of the ABBs 308 identified in the LogicalLevel 0 310 and 1 311 Models. Those models 310, 311, the relationships309 and the ABBs 308 were all designed based on a common set ofPrinciples 307, identified to satisfy Key Requirements 306, derived fromthe ESD Technical Architecture Scope 305 and Objectives 304, which allwere developed to drive toward the ESD Technical Architecture Vision303.

With the complete set of Design Objects 313 identified for BWB, specificTool Selection Criteria 315 were defined (step 206). For example, fromthe Technical Model 301, it was known that all the systems managementtools selected had to be capable of working on all of the platforms(servers, workstations, etc.) that were in the customer environment.From the attributes identified in the Design Objects 313, it was knownwhat that list of platforms was, so criteria were identified that statedthat the “tool for storing and forwarding events must execute on Windows95, Window NT, and AIX Operating systems, etc.”

With the defined Tool Selection Criteria 315, all the specific tools(including hardware and software) were selected, and based on theSpecific Solution Requirements 314, and Solution Scope 317, in step 207,a Detailed Technical Design 316 for the systems management environmentwas developed. FIG. 16 illustrates an example of such Tool Selection. Inthis example, a design object has been identified that includes amainframe, a data store, a hub and a management server. For each ofthese parts of the design object, it is known how they relate, or arecombined to provide functionality. Based on the servers needed to beprovided (in this example, problem management and event management) itis known what relationships between these components are required. Theserequirements are used to evaluate available tools to select tools thatsatisfy all the relational requirements contained in the design object.FIG. 17 illustrates an example of a detailed Technical Design withDesign Objects for the BWB example. When it is known that all of therequirements have been satisfied dictated by the relationships describedin the design objects by selecting all the appropriate tools (softwareand hardware), a consistent, low level design can be created of the ESMsolution. By maintaining all relationships, integration is ensured intothe overall systems management environment. This example illustratescomponents (such as Netview Server, Tivoli Enterprise Console, hubs,routers, etc.) that would be selected and deployed based on the method.

By using this method, a specific Technical Framework 302 was designedfor BWB that satisfied all of their requirements for Problem and EventManagement. Though the maintenance of relationships described in themodel, the systems management solution for BWB provided the capabilityto deliver services in the most efficient and effective way, andfacilitated delivering those services using common, standard technology,practices, etc., across all customer platforms (i.e. server,workstation, mainframe, network component, etc.)

In addition, should the scope of the support requirement/contractchange, the ESDTM and the TDF define the model and the framework intowhich the components of the new service can be fitted, in such a way asto ensure that the entire new solution is part of one comprehensiveservice offering. The methodology describes how the enhanced service canbe rolled out in a way which is effective, efficient and consistentacross all of the service delivery organization.

Referring first to FIG. 18, an example is shown of a data processingsystem 1800 which may be used for the invention. The system has acentral processing unit (CPU) 1810, which is coupled to various othercomponents by system bus 1812. Read only memory (“ROM”) 1816 is coupledto the system bus 1812 and includes a basic input/output system (“BIOS”)that controls certain basic functions of the data processing system1800. Random access memory (“RAM”) 1814, I/O adapter 1818, andcommunications adapter 1834 are also coupled to the system bus 1812. I/Oadapter 1818 may be a small computer system interface (“SCSI”) adapterthat communicates with a disk storage device 1820. Communicationsadapter 1834 interconnects bus 1812 with an outside network enabling thedata processing system to communicate with other such systems.Input/Output devices are also connected to system bus 1812 via userinterface adapter 1822 and display adapter 1836. Keyboard 1824, trackball 1832, mouse 1826 and speaker 1828 are all interconnected to bus1812 via user interface adapter 1822. Display monitor 1838 is connectedto system bus 1812 by display adapter 1836. In this manner, a user iscapable of inputting to the system throughout the keyboard 1824,trackball 1832 or mouse 1826 and receiving output from the system viaspeaker 1828 and display 1838.

Implementations of the invention include implementations as a computersystem programmed to execute the method or methods described herein, andas a computer program product. According to the computer systemimplementation, sets of instructions for executing the method or methodsmay be resident in the random access memory 1814 of one or more computersystems configured generally as described above. Until required by thecomputer system, the set of instructions may be stored as a computerprogram product in another computer memory, for example, in disk drive1820 (which may include a removable memory such as an optical disk orfloppy disk for eventual use in the disk drive 1820). Further, thecomputer program product can also be stored at another computer andtransmitted when desired to the user's work station by a network or byan external network such as the Internet. One skilled in the art wouldappreciate that the physical storage of the sets of instructionsphysically changes the medium upon which it is stored so that the mediumcarries computer readable information. The change may be electrical,magnetic, chemical, biological, or some other physical change. While itis convenient to describe the invention in terms of instructions,symbols, characters, or the like, the reader should remember that all ofthese and similar terms should be associated with the appropriatephysical elements.

Note that the invention may describe terms such as comparing,validating, selecting, identifying, or other terms that could beassociated with a human operator. However, for at least a number of theoperations described herein which form part of at least one of theembodiments, no action by a human operator is desirable. The operationsdescribed are, in large part, machine operations processing electricalsignals to generate other electrical signals.

Although the present invention and its advantages have been described indetail, it should be understood that various changes, substitutions andalterations can be made herein without departing from the spirit andscope of the invention as defined by the appended claims.

1-24. (canceled)
 25. A computer program product stored on a storablecomputer readable medium, the computer program product, when executed ona computer, causes the computer to create an information technologytechnical architecture comprising the program steps of: identifying aSystems Management solution scope specific to an information technologyenvironment of the customer; inventorying existing informationtechnology and Systems Management components supporting the informationtechnology environment of the customer that are within the SystemsManagement solution scope; mapping the existing information technologyand Systems Management components supporting the information technologyenvironment of the customer to architectural building blocks of apredetermined enterprise service delivery technical model; identifyingwhich architectural building blocks of the predetermined enterpriseservice delivery technical model are required to deliver the SystemsManagement services to the customer in accordance with the SystemsManagement solution scope; and mapping the inventoried existinginformation technology components that were mapped to the architecturalbuilding blocks of the predetermined enterprise service deliverytechnical model to the architectural building blocks of thepredetermined enterprise service delivery technical model that wereidentified as required to deliver the Systems Management services inaccordance with the Systems Management solution scope, this mapping stepresulting in a list of design objects and relationships between thedesign objects that will deliver the Systems Management services inaccordance with the Systems Management solution scope.
 26. The computerprogram product as recited in claim 25, wherein the architecturalbuilding blocks and defined relationships between the architecturalbuilding blocks are a function of a set of predefined principles and keyrequirements.
 27. The computer program product as recited in claim 25,wherein relationships between the architectural building blocks arearranged in predefined logical levels.